Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b360d9cff2fe83547a1e098c7f989ff1e7c9dd62e72520b93278d633bdb6d60

Tx prefix hash: 6842642b9ba726e0202c84872b08dbc65ef1e8999ce463f677ccd74f5d150759
Tx public key: b2e864e466c1b518f519efe4b86e1d70832a95f03f38fb96fe2da9a05caaab11
Timestamp: 1676539534 Timestamp [UCT]: 2023-02-16 09:25:34 Age [y:d:h:m:s]: 02:265:22:32:06
Block: 698125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 709390 RingCT/type: yes/0
Extra: 01b2e864e466c1b518f519efe4b86e1d70832a95f03f38fb96fe2da9a05caaab1102110000000474b6d784000000000000000000

1 output(s) for total of 2.984159181000 dcy

stealth address amount amount idx
00: b43b4a39f7f9429be0fcfad2946f44204acd0617b0fc8f532470a9cc70fae333 2.984159181000 1141406 of 0

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": 698135, "vin": [ { "gen": { "height": 698125 } } ], "vout": [ { "amount": 2984159181, "target": { "key": "b43b4a39f7f9429be0fcfad2946f44204acd0617b0fc8f532470a9cc70fae333" } } ], "extra": [ 1, 178, 232, 100, 228, 102, 193, 181, 24, 245, 25, 239, 228, 184, 110, 29, 112, 131, 42, 149, 240, 63, 56, 251, 150, 254, 45, 169, 160, 92, 170, 171, 17, 2, 17, 0, 0, 0, 4, 116, 182, 215, 132, 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