Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72992773558d2333f2996fdb1b9d328eca94656c8532a18a67798718f7bc11c4

Tx prefix hash: 5fbdb2d755b3c093a78f8174835f8c0c398f86f190e16f833eeefeb4841ece9a
Tx public key: 9d937acd056e26e511e8f1eeba78e5f4f7ca25f4106bb6afb2cbbdf7c9484a2e
Timestamp: 1697944036 Timestamp [UCT]: 2023-10-22 03:07:16 Age [y:d:h:m:s]: 01:125:05:05:59
Block: 874905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350460 RingCT/type: yes/0
Extra: 019d937acd056e26e511e8f1eeba78e5f4f7ca25f4106bb6afb2cbbdf7c9484a2e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.774598345000 dcy

stealth address amount amount idx
00: 2c2e1cd74b12b137749d1aa310e5ba2d28c53d8e0b959064daa34790da3af89a 0.774598345000 1330141 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": 874915, "vin": [ { "gen": { "height": 874905 } } ], "vout": [ { "amount": 774598345, "target": { "key": "2c2e1cd74b12b137749d1aa310e5ba2d28c53d8e0b959064daa34790da3af89a" } } ], "extra": [ 1, 157, 147, 122, 205, 5, 110, 38, 229, 17, 232, 241, 238, 186, 120, 229, 244, 247, 202, 37, 244, 16, 107, 182, 175, 178, 203, 189, 247, 201, 72, 74, 46, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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