Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ffb47c8aa23cd7e729b7666d59e1edad502ce6d7fe85f9b137268f7213d9c6e

Tx prefix hash: a58356e30d35ed192945003e0fc78c9cfe9d8ff8fcc2db23f729135871df86f1
Tx public key: f48d440c2b88682af7321e9c95a8efbadbb780d5e463bdca8afbe0760fc9de9d
Timestamp: 1729053227 Timestamp [UCT]: 2024-10-16 04:33:47 Age [y:d:h:m:s]: 00:000:18:58:12
Block: 1132635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543 RingCT/type: yes/0
Extra: 01f48d440c2b88682af7321e9c95a8efbadbb780d5e463bdca8afbe0760fc9de9d0211000000113cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 013a4ac017af97ae4cc4dee6ea627fd739d869e2f7c95f896a8c3e791347ed21 0.600000000000 1615596 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": 1132645, "vin": [ { "gen": { "height": 1132635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "013a4ac017af97ae4cc4dee6ea627fd739d869e2f7c95f896a8c3e791347ed21" } } ], "extra": [ 1, 244, 141, 68, 12, 43, 136, 104, 42, 247, 50, 30, 156, 149, 168, 239, 186, 219, 183, 128, 213, 228, 99, 189, 202, 138, 251, 224, 118, 15, 201, 222, 157, 2, 17, 0, 0, 0, 17, 60, 208, 252, 6, 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