Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 107d6c76e6659d641ef90d329bd3da71f28d91c77156b6a24fca42e1373d0e83

Tx prefix hash: 718f5b965d66ca64e51c7b59858e8c17b4e0b24f2cedda3f9cf6609d776ca927
Tx public key: f71d8f8cff98e041cf3764a424d753d78ad56b7422106479fb16e96d452d537a
Timestamp: 1716492120 Timestamp [UCT]: 2024-05-23 19:22:00 Age [y:d:h:m:s]: 00:315:14:46:41
Block: 1028480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225579 RingCT/type: yes/0
Extra: 01f71d8f8cff98e041cf3764a424d753d78ad56b7422106479fb16e96d452d537a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c66ef2fdca94a30715d3c876706b5184b8f4426a0241322bdeb13b8d56f02b1d 0.600000000000 1496473 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": 1028490, "vin": [ { "gen": { "height": 1028480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c66ef2fdca94a30715d3c876706b5184b8f4426a0241322bdeb13b8d56f02b1d" } } ], "extra": [ 1, 247, 29, 143, 140, 255, 152, 224, 65, 207, 55, 100, 164, 36, 215, 83, 215, 138, 213, 107, 116, 34, 16, 100, 121, 251, 22, 233, 109, 69, 45, 83, 122, 2, 17, 0, 0, 0, 2, 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