Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5bc62e66d1c21f25709ea5c479d6c0eb7255722df9b93e64de5f6a1ad1f95d0

Tx prefix hash: e603c1f36704cfa9f7a5dd41c2000dd99aaa0e63cf6a166f0755ae75f9579adb
Tx public key: 8835fdbf00f3bf01f3ecdda5af2ca85eda06ae120b9b4de042c32cdc044fd811
Timestamp: 1719754368 Timestamp [UCT]: 2024-06-30 13:32:48 Age [y:d:h:m:s]: 00:258:07:23:54
Block: 1055510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184580 RingCT/type: yes/0
Extra: 018835fdbf00f3bf01f3ecdda5af2ca85eda06ae120b9b4de042c32cdc044fd8110211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8de2ef8a9db8ee2a0b8cfeff44544b76566665a2b27a84889d018b5e436210d4 0.600000000000 1525915 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": 1055520, "vin": [ { "gen": { "height": 1055510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8de2ef8a9db8ee2a0b8cfeff44544b76566665a2b27a84889d018b5e436210d4" } } ], "extra": [ 1, 136, 53, 253, 191, 0, 243, 191, 1, 243, 236, 221, 165, 175, 44, 168, 94, 218, 6, 174, 18, 11, 155, 77, 224, 66, 195, 44, 220, 4, 79, 216, 17, 2, 17, 0, 0, 0, 1, 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