Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04f45da3f1c965262299f90394479e32621c26ddfc4d0f68185b01c7690e41d8

Tx prefix hash: 99a678debdb0d428cc7e2424605192033f0ff3d6e7456598e7acf1effaa628b4
Tx public key: c67df620f9bcd4f4271413bbf30cf86dd50ce5913404e5d86f4d027dd3be84f7
Timestamp: 1736625476 Timestamp [UCT]: 2025-01-11 19:57:56 Age [y:d:h:m:s]: 00:069:03:50:45
Block: 1195235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49213 RingCT/type: yes/0
Extra: 01c67df620f9bcd4f4271413bbf30cf86dd50ce5913404e5d86f4d027dd3be84f70211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7b25bbf0a83e2cab5204b4348d8c77c60d4d0788d7f9c7d791386c112c236f2 0.600000000000 1681824 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": 1195245, "vin": [ { "gen": { "height": 1195235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7b25bbf0a83e2cab5204b4348d8c77c60d4d0788d7f9c7d791386c112c236f2" } } ], "extra": [ 1, 198, 125, 246, 32, 249, 188, 212, 244, 39, 20, 19, 187, 243, 12, 248, 109, 213, 12, 229, 145, 52, 4, 229, 216, 111, 77, 2, 125, 211, 190, 132, 247, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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