Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea9035d1ada6c09b2dd3acbb8d3d8e5bd22ab2d7465c98471aae81b2de5b62a

Tx prefix hash: de29b9970b5d9c9ea7d4a40b17af4d5387ce71fa52b1739f0278ac8e7c93f983
Tx public key: 0cf356f14f29635529fdd2b2f42c93b2ad6b3e5bf68b972718e6fc85594a049d
Timestamp: 1648871074 Timestamp [UCT]: 2022-04-02 03:44:34 Age [y:d:h:m:s]: 02:347:11:52:43
Block: 471375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 767839 RingCT/type: yes/0
Extra: 010cf356f14f29635529fdd2b2f42c93b2ad6b3e5bf68b972718e6fc85594a049d02110000000537cb3088000000000000000000

1 output(s) for total of 16.832134600000 dcy

stealth address amount amount idx
00: 0b3f6adca2eba771d018b7455f5281192ec724c856a7954c7bc0534a27f9e58d 16.832134600000 890703 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": 471385, "vin": [ { "gen": { "height": 471375 } } ], "vout": [ { "amount": 16832134600, "target": { "key": "0b3f6adca2eba771d018b7455f5281192ec724c856a7954c7bc0534a27f9e58d" } } ], "extra": [ 1, 12, 243, 86, 241, 79, 41, 99, 85, 41, 253, 210, 178, 244, 44, 147, 178, 173, 107, 62, 91, 246, 139, 151, 39, 24, 230, 252, 133, 89, 74, 4, 157, 2, 17, 0, 0, 0, 5, 55, 203, 48, 136, 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