Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0b7c9062edb89a5a8ba4d03addfda599ed8f138ab1d8ad832b0844c0e20cbd8

Tx prefix hash: 4eda97fee82f941a39887758c697c9b1866f8c37bf8d74e60f30dc29b5b1c0d5
Tx public key: 17a69449fde937aa50d23b5535ec7a46e36e82e8478fe859faaa905a683f8929
Timestamp: 1737623222 Timestamp [UCT]: 2025-01-23 09:07:02 Age [y:d:h:m:s]: 00:147:13:04:47
Block: 1203464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105170 RingCT/type: yes/0
Extra: 0117a69449fde937aa50d23b5535ec7a46e36e82e8478fe859faaa905a683f89290211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ad67ddb06f6281f219a56cd1ef3f6612cce2c6833d19b64c9650a1fb77f2ed2 0.600000000000 1690141 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": 1203474, "vin": [ { "gen": { "height": 1203464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ad67ddb06f6281f219a56cd1ef3f6612cce2c6833d19b64c9650a1fb77f2ed2" } } ], "extra": [ 1, 23, 166, 148, 73, 253, 233, 55, 170, 80, 210, 59, 85, 53, 236, 122, 70, 227, 110, 130, 232, 71, 143, 232, 89, 250, 170, 144, 90, 104, 63, 137, 41, 2, 17, 0, 0, 0, 5, 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