Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a0f95b3740a0b9ae300dfd79e8be14fb447ca08a6bb67221ecbee98fa76030d

Tx prefix hash: 4cd2c912963938851008a4f15bb07309f1e57a1e424b987f2f9668339b4db89a
Tx public key: d5530b70397f62181de2fa766c3c3ab02fb5c9efbec3610a878376e7930fc0f9
Timestamp: 1709398505 Timestamp [UCT]: 2024-03-02 16:55:05 Age [y:d:h:m:s]: 01:021:02:00:36
Block: 969670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276062 RingCT/type: yes/0
Extra: 01d5530b70397f62181de2fa766c3c3ab02fb5c9efbec3610a878376e7930fc0f902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69a31790c69c6a4984c3ec4d2fabfc8d35be6eb1238cb28204cdd1740d346655 0.600000000000 1429507 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": 969680, "vin": [ { "gen": { "height": 969670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69a31790c69c6a4984c3ec4d2fabfc8d35be6eb1238cb28204cdd1740d346655" } } ], "extra": [ 1, 213, 83, 11, 112, 57, 127, 98, 24, 29, 226, 250, 118, 108, 60, 58, 176, 47, 181, 201, 239, 190, 195, 97, 10, 135, 131, 118, 231, 147, 15, 192, 249, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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