Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72e55937bfbb510e751f78cf28ac06fe661824f0410e0a05e294436e6f1cc526

Tx prefix hash: f400bc4501c6e060aa9aecd85712c87036989d3fa570eb2587a376aa862f3096
Tx public key: 183ea45e3929f8fdd4ea00f779b5a040955b6e0484e40c411e01f827020a3acf
Timestamp: 1718890882 Timestamp [UCT]: 2024-06-20 13:41:22 Age [y:d:h:m:s]: 00:278:17:58:44
Block: 1048363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199168 RingCT/type: yes/0
Extra: 01183ea45e3929f8fdd4ea00f779b5a040955b6e0484e40c411e01f827020a3acf02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79099d2ff06043221b13503f75416ea80ae9c4ef1a7187cd3b67533cd9a63cc5 0.600000000000 1518432 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": 1048373, "vin": [ { "gen": { "height": 1048363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79099d2ff06043221b13503f75416ea80ae9c4ef1a7187cd3b67533cd9a63cc5" } } ], "extra": [ 1, 24, 62, 164, 94, 57, 41, 248, 253, 212, 234, 0, 247, 121, 181, 160, 64, 149, 91, 110, 4, 132, 228, 12, 65, 30, 1, 248, 39, 2, 10, 58, 207, 2, 17, 0, 0, 0, 5, 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