Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3033ee0e99a1e68c267f553381d2ba0f96940f151018a6ada54875776a09e1a3

Tx prefix hash: 70765a41b3e6e100537532355194f7bb3a528378f4f3aea18d76bbc4e7b72e70
Tx public key: 453af61378b16af92ff9eb92324cdb83e1f6a833ca16798c5a2c670f2c20aaf3
Timestamp: 1712996103 Timestamp [UCT]: 2024-04-13 08:15:03 Age [y:d:h:m:s]: 00:318:02:22:16
Block: 999469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227408 RingCT/type: yes/0
Extra: 01453af61378b16af92ff9eb92324cdb83e1f6a833ca16798c5a2c670f2c20aaf30211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc2129e6d6f427f7ebc60f4da4d4778fb2b3b59ed1e829c942f5fa0ce4008766 0.600000000000 1459949 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": 999479, "vin": [ { "gen": { "height": 999469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc2129e6d6f427f7ebc60f4da4d4778fb2b3b59ed1e829c942f5fa0ce4008766" } } ], "extra": [ 1, 69, 58, 246, 19, 120, 177, 106, 249, 47, 249, 235, 146, 50, 76, 219, 131, 225, 246, 168, 51, 202, 22, 121, 140, 90, 44, 103, 15, 44, 32, 170, 243, 2, 17, 0, 0, 0, 3, 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