Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a62cb8e808fd67f24734db4ca0a5e007444aaa8f991438e7cfaf62fbb5d1c70

Tx prefix hash: 87cd088b7f1965b4770d26bee7a2838bbc9441598ea2582cc29ee5f0b11f591b
Tx public key: 9351456d31d2d0c65f4182821bb5309e1efd7b1c6d1797268af384c806e6552b
Timestamp: 1713996001 Timestamp [UCT]: 2024-04-24 22:00:01 Age [y:d:h:m:s]: 01:013:21:24:34
Block: 1007783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270859 RingCT/type: yes/0
Extra: 019351456d31d2d0c65f4182821bb5309e1efd7b1c6d1797268af384c806e6552b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a42ac5f3c483b3a6d7a11b3ec0dfd7505936b950b3e439f5091008d1a268ff4 0.600000000000 1469231 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": 1007793, "vin": [ { "gen": { "height": 1007783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a42ac5f3c483b3a6d7a11b3ec0dfd7505936b950b3e439f5091008d1a268ff4" } } ], "extra": [ 1, 147, 81, 69, 109, 49, 210, 208, 198, 95, 65, 130, 130, 27, 181, 48, 158, 30, 253, 123, 28, 109, 23, 151, 38, 138, 243, 132, 200, 6, 230, 85, 43, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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