Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef5abe388b3eea72529fc0b9ea4cc24dccc7f37d8066474fa09070db41625c23

Tx prefix hash: 567fc593b77df3149fbf5932a32fb83a4dd94ee1cf423331b4cfc48479d7bbf4
Tx public key: b73f9b1a1ebf7db2bc4f3655dccc3e634a4a9c5adfeda5a87bdd8f3f5de21240
Timestamp: 1681935222 Timestamp [UCT]: 2023-04-19 20:13:42 Age [y:d:h:m:s]: 01:310:13:21:25
Block: 742225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483184 RingCT/type: yes/0
Extra: 01b73f9b1a1ebf7db2bc4f3655dccc3e634a4a9c5adfeda5a87bdd8f3f5de21240021100000002b3164c24000000000000000000

1 output(s) for total of 2.131575291000 dcy

stealth address amount amount idx
00: d7b449708d84f07190bc9c851c7c32cc37ff17fc7991c8ba5dbd1e231d013076 2.131575291000 1189184 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": 742235, "vin": [ { "gen": { "height": 742225 } } ], "vout": [ { "amount": 2131575291, "target": { "key": "d7b449708d84f07190bc9c851c7c32cc37ff17fc7991c8ba5dbd1e231d013076" } } ], "extra": [ 1, 183, 63, 155, 26, 30, 191, 125, 178, 188, 79, 54, 85, 220, 204, 62, 99, 74, 74, 156, 90, 223, 237, 165, 168, 123, 221, 143, 63, 93, 226, 18, 64, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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