Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fa273a24f33a3827833cf3d14765755e3ab534032dc60cea54d4c5aef8f6dd4

Tx prefix hash: ebf4b95c4c166b411e902d0c4d06ef3105f617c03e2b2b9fb7b0e11e4b7db6a8
Tx public key: 84e1b1a97e4ec29a6060a9a7dfee1eb2bfccd337ab518ac4aae9cd77fbefe2c5
Timestamp: 1723107222 Timestamp [UCT]: 2024-08-08 08:53:42 Age [y:d:h:m:s]: 01:090:13:17:53
Block: 1083319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323183 RingCT/type: yes/0
Extra: 0184e1b1a97e4ec29a6060a9a7dfee1eb2bfccd337ab518ac4aae9cd77fbefe2c5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 613fad59ab90b9f8364ae5b41d4617038010d295259092dfb6f2e537207a0c22 0.600000000000 1557186 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": 1083329, "vin": [ { "gen": { "height": 1083319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "613fad59ab90b9f8364ae5b41d4617038010d295259092dfb6f2e537207a0c22" } } ], "extra": [ 1, 132, 225, 177, 169, 126, 78, 194, 154, 96, 96, 169, 167, 223, 238, 30, 178, 191, 204, 211, 55, 171, 81, 138, 196, 170, 233, 205, 119, 251, 239, 226, 197, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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