Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fa2999b6fdc0caf454b3abd903076271b2603a2858e1e1b81942a6396de0a5a

Tx prefix hash: 5739d8fe4369419568552ffc6d279e22409745d4a40a1f2299042d5a9d80bcf1
Tx public key: 900aaa00fa424a8b81d7eb85b77a717aba4353dc4cfc367dc3608e0b24913ee7
Timestamp: 1728515319 Timestamp [UCT]: 2024-10-09 23:08:39 Age [y:d:h:m:s]: 00:178:04:17:54
Block: 1128147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127130 RingCT/type: yes/0
Extra: 01900aaa00fa424a8b81d7eb85b77a717aba4353dc4cfc367dc3608e0b24913ee7021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb4ddc4a5c08e99f7ff054e90ad3065d44e1a8f4c596b7d1207765c49e506a12 0.600000000000 1610964 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": 1128157, "vin": [ { "gen": { "height": 1128147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb4ddc4a5c08e99f7ff054e90ad3065d44e1a8f4c596b7d1207765c49e506a12" } } ], "extra": [ 1, 144, 10, 170, 0, 250, 66, 74, 139, 129, 215, 235, 133, 183, 122, 113, 122, 186, 67, 83, 220, 76, 252, 54, 125, 195, 96, 142, 11, 36, 145, 62, 231, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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