Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e4b1ce3da68d6769ff44c83ccdc5f91f715f1e0cbe0897e674b601db15bf17

Tx prefix hash: f92014e4541d7c88c3bc1fed5adfbc6dc26db2b8e038f321bd1034a289e66d83
Tx public key: 778a91b1a42d803acc22d359d62efd92ed13668e498b2505e9a82e9429fc1450
Timestamp: 1712318919 Timestamp [UCT]: 2024-04-05 12:08:39 Age [y:d:h:m:s]: 01:218:01:43:32
Block: 993848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414563 RingCT/type: yes/0
Extra: 01778a91b1a42d803acc22d359d62efd92ed13668e498b2505e9a82e9429fc145002110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4e2d263c9dd31d03f6044b5939649489f8a526f163962b78a9bbd3a1be953cd 0.600000000000 1454236 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": 993858, "vin": [ { "gen": { "height": 993848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4e2d263c9dd31d03f6044b5939649489f8a526f163962b78a9bbd3a1be953cd" } } ], "extra": [ 1, 119, 138, 145, 177, 164, 45, 128, 58, 204, 34, 211, 89, 214, 46, 253, 146, 237, 19, 102, 142, 73, 139, 37, 5, 233, 168, 46, 148, 41, 252, 20, 80, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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