Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c30d8b72f7cc45a4cb970763e99ba9d08733688551af25611191104665dc373

Tx prefix hash: 44251609d85ac4920193b528aeff8084ab07a786b8c6e3c96d893a6bd85c6ba9
Tx public key: 7ab23f110efb334ea35bbefe54e8cf42c6c2ea18be3216c25c82e6cd58f587fc
Timestamp: 1720460885 Timestamp [UCT]: 2024-07-08 17:48:05 Age [y:d:h:m:s]: 01:122:20:15:20
Block: 1061384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346310 RingCT/type: yes/0
Extra: 017ab23f110efb334ea35bbefe54e8cf42c6c2ea18be3216c25c82e6cd58f587fc02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e9b60b15d3bee6b69fd5a11dacf97a9aa1afc56b66a6a23c0766782d7c30355 0.600000000000 1531875 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": 1061394, "vin": [ { "gen": { "height": 1061384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e9b60b15d3bee6b69fd5a11dacf97a9aa1afc56b66a6a23c0766782d7c30355" } } ], "extra": [ 1, 122, 178, 63, 17, 14, 251, 51, 78, 163, 91, 190, 254, 84, 232, 207, 66, 198, 194, 234, 24, 190, 50, 22, 194, 92, 130, 230, 205, 88, 245, 135, 252, 2, 17, 0, 0, 0, 10, 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