Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12753a4ce7cc5c7699ff1fdbbed8d91eedecccb0b5b81baa1b08c2ce14002393

Tx prefix hash: 5ded7e9402f1f42c5f577ec1f7f51f51c11caae3ebc08f9055147f0213209aa1
Tx public key: d6f8dc488b94dbbe672787df4bbcbd83ebc6b9a3714562be1ec6d8249cc14dc9
Timestamp: 1713203633 Timestamp [UCT]: 2024-04-15 17:53:53 Age [y:d:h:m:s]: 01:050:03:40:20
Block: 1001193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296850 RingCT/type: yes/0
Extra: 01d6f8dc488b94dbbe672787df4bbcbd83ebc6b9a3714562be1ec6d8249cc14dc9021100000004679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdb09dcf2b03e454ab8c6e56c13639819c489237fabac27473d920705f6ce917 0.600000000000 1461695 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": 1001203, "vin": [ { "gen": { "height": 1001193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdb09dcf2b03e454ab8c6e56c13639819c489237fabac27473d920705f6ce917" } } ], "extra": [ 1, 214, 248, 220, 72, 139, 148, 219, 190, 103, 39, 135, 223, 75, 188, 189, 131, 235, 198, 185, 163, 113, 69, 98, 190, 30, 198, 216, 36, 156, 193, 77, 201, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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