Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88240c5984af3fc4838233e5963bc6c7fa3cee7588fed5d2efbf5e0ece8e0934

Tx prefix hash: 9225ff2a11e03605772b3867d8e37a2e4e26a3ee8125b2f3c43302aae9e5a9aa
Tx public key: 9eb4378d3740d8d55c97f2b3b546b07f6670d665da81771931c94052845ff2e8
Timestamp: 1728104769 Timestamp [UCT]: 2024-10-05 05:06:09 Age [y:d:h:m:s]: 00:231:19:13:36
Block: 1124747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165504 RingCT/type: yes/0
Extra: 019eb4378d3740d8d55c97f2b3b546b07f6670d665da81771931c94052845ff2e802110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a996d35e79c18c729d15c04279d2a316f9ffe28e6253a3f2b3076425720164a9 0.600000000000 1607414 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": 1124757, "vin": [ { "gen": { "height": 1124747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a996d35e79c18c729d15c04279d2a316f9ffe28e6253a3f2b3076425720164a9" } } ], "extra": [ 1, 158, 180, 55, 141, 55, 64, 216, 213, 92, 151, 242, 179, 181, 70, 176, 127, 102, 112, 214, 101, 218, 129, 119, 25, 49, 201, 64, 82, 132, 95, 242, 232, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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