Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ce0f5165a1a59689c5b000f83e564b705cfae47584dcb6faa5f1e537697b311

Tx prefix hash: 916cbf750e94f0bd0917bcaa1c0f3274270e3bf68a1cfbfc7f911806cb4bdc7b
Tx public key: 069c00744ae4e59ede524f54ec8196eca3811d2e25c54759f93d874a180d7ce1
Timestamp: 1726145851 Timestamp [UCT]: 2024-09-12 12:57:31 Age [y:d:h:m:s]: 00:194:10:33:36
Block: 1108499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138789 RingCT/type: yes/0
Extra: 01069c00744ae4e59ede524f54ec8196eca3811d2e25c54759f93d874a180d7ce102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cf8b0d976a3095221638231d798dbf8ca790cdd90f9be1eac5edc1b4b9683d7 0.600000000000 1586416 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": 1108509, "vin": [ { "gen": { "height": 1108499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cf8b0d976a3095221638231d798dbf8ca790cdd90f9be1eac5edc1b4b9683d7" } } ], "extra": [ 1, 6, 156, 0, 116, 74, 228, 229, 158, 222, 82, 79, 84, 236, 129, 150, 236, 163, 129, 29, 46, 37, 197, 71, 89, 249, 61, 135, 74, 24, 13, 124, 225, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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