Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 508ae943c65aac7e158a80dc933b1a7eda8e098a276fead9e5d681205ace6d16

Tx prefix hash: 7d674ddf1b38e82260486f9e43ff1a0dfa7ff76cc957a0c1fe8589cc52b0dbfe
Tx public key: fe105678f442fe748d2a3d514751ebfdd6a09891f03ad46a9a3bbd57b9247a68
Timestamp: 1706129197 Timestamp [UCT]: 2024-01-24 20:46:37 Age [y:d:h:m:s]: 01:280:15:19:34
Block: 942531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459384 RingCT/type: yes/0
Extra: 01fe105678f442fe748d2a3d514751ebfdd6a09891f03ad46a9a3bbd57b9247a6802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 934b5c5dd10befac1fa657796f36b57fd8086354fb8f67d1910095a406d09ae6 0.600000000000 1400705 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 942541, "vin": [ { "gen": { "height": 942531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "934b5c5dd10befac1fa657796f36b57fd8086354fb8f67d1910095a406d09ae6" } } ], "extra": [ 1, 254, 16, 86, 120, 244, 66, 254, 116, 141, 42, 61, 81, 71, 81, 235, 253, 214, 160, 152, 145, 240, 58, 212, 106, 154, 59, 189, 87, 185, 36, 122, 104, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8