Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5317656f5ce8b8e7abb1e8d85a36532ba5424fe15370944086f7c7013586120a

Tx prefix hash: dde5a1e94ee0deb2d29cdc490d6fd3b6c2a26b7d9494034ffa61542f0bccc8e3
Tx public key: 0eec2a638c46b71e253f9fef3a101c3e5a4491338a99504c6d67ab23a35e87f9
Timestamp: 1711447619 Timestamp [UCT]: 2024-03-26 10:06:59 Age [y:d:h:m:s]: 00:287:03:35:14
Block: 986674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205528 RingCT/type: yes/0
Extra: 010eec2a638c46b71e253f9fef3a101c3e5a4491338a99504c6d67ab23a35e87f90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25027a05bc001dc4c55d96a6e9f1aa3a513716bb352f77734cf633bb07eea4dc 0.600000000000 1446907 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": 986684, "vin": [ { "gen": { "height": 986674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25027a05bc001dc4c55d96a6e9f1aa3a513716bb352f77734cf633bb07eea4dc" } } ], "extra": [ 1, 14, 236, 42, 99, 140, 70, 183, 30, 37, 63, 159, 239, 58, 16, 28, 62, 90, 68, 145, 51, 138, 153, 80, 76, 109, 103, 171, 35, 163, 94, 135, 249, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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