Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37196466f14c22a84e99cc1245845df7a526924ea0d261e338f79ac236d4b316

Tx prefix hash: 9e8246c9736439f3901c58c0e439e0026ebaa5ba15ae31237b3bf2199fd31fd8
Tx public key: 9a61e7ecb5164201970e8225ec1b4fddda4aaea6d90e83b1dfe93f4266384773
Timestamp: 1710846706 Timestamp [UCT]: 2024-03-19 11:11:46 Age [y:d:h:m:s]: 01:042:23:18:18
Block: 981689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291682 RingCT/type: yes/0
Extra: 019a61e7ecb5164201970e8225ec1b4fddda4aaea6d90e83b1dfe93f426638477302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bede37e9b58ee680a343d2bed471b22c008f36f91344f8ccdbc1b84edf98536 0.600000000000 1441786 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": 981699, "vin": [ { "gen": { "height": 981689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bede37e9b58ee680a343d2bed471b22c008f36f91344f8ccdbc1b84edf98536" } } ], "extra": [ 1, 154, 97, 231, 236, 181, 22, 66, 1, 151, 14, 130, 37, 236, 27, 79, 221, 218, 74, 174, 166, 217, 14, 131, 177, 223, 233, 63, 66, 102, 56, 71, 115, 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