Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2499c7807fc4a5a4c57082b84dcfa160a69cb9de15db3266a7d6a06e26c026f4

Tx prefix hash: a9901dbec95c80839bac8d4612fb4708969e13931a7957b62ea28295b3c4d671
Tx public key: 22e9863499d8e13516d45c02eead84aa64489d2f7c72f566cbb11cf287c21d4f
Timestamp: 1729482820 Timestamp [UCT]: 2024-10-21 03:53:40 Age [y:d:h:m:s]: 00:207:22:43:05
Block: 1136146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148441 RingCT/type: yes/0
Extra: 0122e9863499d8e13516d45c02eead84aa64489d2f7c72f566cbb11cf287c21d4f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a60ed4a555a326e37aa3d5b503bbf65ef4af7ef95f6bd30fef633b00f36789a1 0.600000000000 1619489 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": 1136156, "vin": [ { "gen": { "height": 1136146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a60ed4a555a326e37aa3d5b503bbf65ef4af7ef95f6bd30fef633b00f36789a1" } } ], "extra": [ 1, 34, 233, 134, 52, 153, 216, 225, 53, 22, 212, 92, 2, 238, 173, 132, 170, 100, 72, 157, 47, 124, 114, 245, 102, 203, 177, 28, 242, 135, 194, 29, 79, 2, 17, 0, 0, 0, 2, 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