Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df688a64519e75a7520badc957e7fec283537c2f12ca8d12d2d58b837215fe69

Tx prefix hash: 0a248b4239c6aa8163b4ba07c5f871567918fa42bdf88ae7e37b842e25851d70
Tx public key: f1d11e4f620e238fdecc2e4673333a2aedb8d949ce03d16ffce3301c85e528f1
Timestamp: 1740990226 Timestamp [UCT]: 2025-03-03 08:23:46 Age [y:d:h:m:s]: 00:256:01:50:49
Block: 1231111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180769 RingCT/type: yes/0
Extra: 01f1d11e4f620e238fdecc2e4673333a2aedb8d949ce03d16ffce3301c85e528f10211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b088a516fba227c838f3dff29eb971b6346bff973a580969a6a407ca65ca3127 0.600000000000 1718016 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": 1231121, "vin": [ { "gen": { "height": 1231111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b088a516fba227c838f3dff29eb971b6346bff973a580969a6a407ca65ca3127" } } ], "extra": [ 1, 241, 209, 30, 79, 98, 14, 35, 143, 222, 204, 46, 70, 115, 51, 58, 42, 237, 184, 217, 73, 206, 3, 209, 111, 252, 227, 48, 28, 133, 229, 40, 241, 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