Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601480f11ea95a721995e7326ce2f0a15c2369ef24e3b7f14e9b12d10a4d3638

Tx prefix hash: 5c749761be1db7d5529443e5bca98b6763d2039c4beee4e74c9bd90ff23a4558
Tx public key: bb60d06dcd343f19ce56a4e0f4d4d0c2c0dcfd4d4731d363ddafcec78a6efc3e
Timestamp: 1744241703 Timestamp [UCT]: 2025-04-09 23:35:03 Age [y:d:h:m:s]: 00:298:14:37:50
Block: 1258026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211077 RingCT/type: yes/0
Extra: 01bb60d06dcd343f19ce56a4e0f4d4d0c2c0dcfd4d4731d363ddafcec78a6efc3e0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec5a7cbd9cdf250a00702c9dc98b4bf1f9315caa729570aefaa3f96e3e473905 0.600000000000 1745157 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": 1258036, "vin": [ { "gen": { "height": 1258026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec5a7cbd9cdf250a00702c9dc98b4bf1f9315caa729570aefaa3f96e3e473905" } } ], "extra": [ 1, 187, 96, 208, 109, 205, 52, 63, 25, 206, 86, 164, 224, 244, 212, 208, 194, 192, 220, 253, 77, 71, 49, 211, 99, 221, 175, 206, 199, 138, 110, 252, 62, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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