Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f0c499af6908d7d80d199eb0b026dfb6b416569746921d67216173b5bdfd28b

Tx prefix hash: 0d0cdd0519ac4077f3eec8e7922e8424c71d1be4aef67f9882e93ddbc64629b3
Tx public key: a3f6e99ae9a986422dd83d4c551ad0be6683a934151896331b62bf23ec2baa84
Timestamp: 1732090397 Timestamp [UCT]: 2024-11-20 08:13:17 Age [y:d:h:m:s]: 00:141:14:36:36
Block: 1157683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101036 RingCT/type: yes/0
Extra: 01a3f6e99ae9a986422dd83d4c551ad0be6683a934151896331b62bf23ec2baa840211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a2bdccb1ae758b21b1cf73c0b49758a81ef902ba353a25c68f90d19bd1cb15c 0.600000000000 1643306 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": 1157693, "vin": [ { "gen": { "height": 1157683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a2bdccb1ae758b21b1cf73c0b49758a81ef902ba353a25c68f90d19bd1cb15c" } } ], "extra": [ 1, 163, 246, 233, 154, 233, 169, 134, 66, 45, 216, 61, 76, 85, 26, 208, 190, 102, 131, 169, 52, 21, 24, 150, 51, 27, 98, 191, 35, 236, 43, 170, 132, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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