Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8ed504dc29a8146c45ba559493e4f46263f6fc7aaa56132e9e1b2051da24cf6

Tx prefix hash: 40f14ef03b3571bf47dda447d6f429f69b29b51781b9670b01058ca5cefdc5f0
Tx public key: 0d3ae505f98d55370cfee545c237502d14f69844478492d0b31d55efb7958af1
Timestamp: 1714213683 Timestamp [UCT]: 2024-04-27 10:28:03 Age [y:d:h:m:s]: 00:346:03:01:48
Block: 1009581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247423 RingCT/type: yes/0
Extra: 010d3ae505f98d55370cfee545c237502d14f69844478492d0b31d55efb7958af10211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41c8b2d8b3f15a42d6a0f0c10e0fb4e31a03e9d5e52e6efa3989121c32834454 0.600000000000 1471297 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": 1009591, "vin": [ { "gen": { "height": 1009581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c8b2d8b3f15a42d6a0f0c10e0fb4e31a03e9d5e52e6efa3989121c32834454" } } ], "extra": [ 1, 13, 58, 229, 5, 249, 141, 85, 55, 12, 254, 229, 69, 194, 55, 80, 45, 20, 246, 152, 68, 71, 132, 146, 208, 179, 29, 85, 239, 183, 149, 138, 241, 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