Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76571730c3c47398648976d5319f77e7c2d2122a63c43ca842348808ab108dba

Tx prefix hash: 2cd8088cdc32d7c9c9302da56d9c765048e70aa5aae6e244a8411ab91195070a
Tx public key: 8848bfda5b90dfe6a5b41c996d29dee6543d7e7d53ef6e25b1d818e688432d3f
Timestamp: 1717009516 Timestamp [UCT]: 2024-05-29 19:05:16 Age [y:d:h:m:s]: 00:351:12:38:01
Block: 1032763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251257 RingCT/type: yes/0
Extra: 018848bfda5b90dfe6a5b41c996d29dee6543d7e7d53ef6e25b1d818e688432d3f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6342422a34396166bd3bd9b990add17d25f961ed4040c3c49fe74f5172010f1e 0.600000000000 1501218 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": 1032773, "vin": [ { "gen": { "height": 1032763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6342422a34396166bd3bd9b990add17d25f961ed4040c3c49fe74f5172010f1e" } } ], "extra": [ 1, 136, 72, 191, 218, 91, 144, 223, 230, 165, 180, 28, 153, 109, 41, 222, 230, 84, 61, 126, 125, 83, 239, 110, 37, 177, 216, 24, 230, 136, 67, 45, 63, 2, 17, 0, 0, 0, 1, 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