Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96737bd76794653645dda063f5614973ea9e142a4d7d046ce8b422489a211dc9

Tx prefix hash: c998b1d0966d13b3802a4f1521d94d6e9f3aec6839cf4f49ef416b380f5c1f87
Tx public key: a0bf83ff440242c0dc5b04716247c327acef2e5b32cfccb6e5384f983951540e
Timestamp: 1704264708 Timestamp [UCT]: 2024-01-03 06:51:48 Age [y:d:h:m:s]: 01:090:07:13:21
Block: 927089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325660 RingCT/type: yes/0
Extra: 01a0bf83ff440242c0dc5b04716247c327acef2e5b32cfccb6e5384f983951540e02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0bf3f263bea01f75884af9738cc23f76102f5896a062e3df16b422f0f49d272 0.600000000000 1384891 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": 927099, "vin": [ { "gen": { "height": 927089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0bf3f263bea01f75884af9738cc23f76102f5896a062e3df16b422f0f49d272" } } ], "extra": [ 1, 160, 191, 131, 255, 68, 2, 66, 192, 220, 91, 4, 113, 98, 71, 195, 39, 172, 239, 46, 91, 50, 207, 204, 182, 229, 56, 79, 152, 57, 81, 84, 14, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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