Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bea1115ee3301d3b559262ebccc3341154427a58dbffec560728925d726b1a4

Tx prefix hash: f405c5ae41be047d1bb5ea3418a24ed59138e3a53e5f9d9e23b6ccb518b38db8
Tx public key: 310f3ff85e9623112422e22ef381ac2ccb2fb0d850edc1f926c0a1f1ee576344
Timestamp: 1757172872 Timestamp [UCT]: 2025-09-06 15:34:32 Age [y:d:h:m:s]: 00:120:00:16:36
Block: 1362726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85851 RingCT/type: yes/0
Extra: 01310f3ff85e9623112422e22ef381ac2ccb2fb0d850edc1f926c0a1f1ee57634402110000000ab2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0692e26a1188cd0d2e09090eec62f0f2365ccbe8f1352fae21cd93ff2534c117 0.600000000000 1850757 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": 1362736, "vin": [ { "gen": { "height": 1362726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0692e26a1188cd0d2e09090eec62f0f2365ccbe8f1352fae21cd93ff2534c117" } } ], "extra": [ 1, 49, 15, 63, 248, 94, 150, 35, 17, 36, 34, 226, 46, 243, 129, 172, 44, 203, 47, 176, 216, 80, 237, 193, 249, 38, 192, 161, 241, 238, 87, 99, 68, 2, 17, 0, 0, 0, 10, 178, 247, 132, 196, 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