Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2965d2fe91f12279250be5f6544c543d7a710e5e0b873b3253ae863ae2f4d6ce

Tx prefix hash: 88e4d0e81ba5480cab4fe76dbf47c6e51e980681e7566e6f0e55a09e1b173e53
Tx public key: 0c3808981d7073794c029511611e0fcebb34756fe2d499cab6e5526dfe87d1f1
Timestamp: 1700774541 Timestamp [UCT]: 2023-11-23 21:22:21 Age [y:d:h:m:s]: 01:356:14:15:38
Block: 898159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513759 RingCT/type: yes/0
Extra: 010c3808981d7073794c029511611e0fcebb34756fe2d499cab6e5526dfe87d1f102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.648673828000 dcy

stealth address amount amount idx
00: 16257fc0eec3abf7b6393998beb28514c651210bb4c2f6f3fa11ec2d4b71355d 0.648673828000 1354564 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": 898169, "vin": [ { "gen": { "height": 898159 } } ], "vout": [ { "amount": 648673828, "target": { "key": "16257fc0eec3abf7b6393998beb28514c651210bb4c2f6f3fa11ec2d4b71355d" } } ], "extra": [ 1, 12, 56, 8, 152, 29, 112, 115, 121, 76, 2, 149, 17, 97, 30, 15, 206, 187, 52, 117, 111, 226, 212, 153, 202, 182, 229, 82, 109, 254, 135, 209, 241, 2, 17, 0, 0, 0, 3, 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