Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f00869b54efcd733f8b2b8f2e5f08e3f014569548a897a7637a1ab836e2f34e1

Tx prefix hash: 3f3b5fb7d91e82ba090564c62ad5725a8efe3464c6c739213a0cb6f787c4e037
Tx public key: cb4206089c32c8af0195319a7900c66d6bae977115472e56c07c7acc0abef979
Timestamp: 1702857389 Timestamp [UCT]: 2023-12-17 23:56:29 Age [y:d:h:m:s]: 01:250:01:42:51
Block: 915439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437647 RingCT/type: yes/0
Extra: 01cb4206089c32c8af0195319a7900c66d6bae977115472e56c07c7acc0abef979021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8817cd65e5c243b349c3d6b816c74bcd64e8c39512a6f88da335eb8fcb4e57f 0.600000000000 1372835 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": 915449, "vin": [ { "gen": { "height": 915439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8817cd65e5c243b349c3d6b816c74bcd64e8c39512a6f88da335eb8fcb4e57f" } } ], "extra": [ 1, 203, 66, 6, 8, 156, 50, 200, 175, 1, 149, 49, 154, 121, 0, 198, 109, 107, 174, 151, 113, 21, 71, 46, 86, 192, 124, 122, 204, 10, 190, 249, 121, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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