Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 614adff7cd271b73d0632f8878b4fa30dd670d4cbe295cc5407866bd9e39d5b3

Tx prefix hash: 932500347b68d57239c3aa4187d9bcf4b04bf56265b746d6b8bfd3da63c2832b
Tx public key: 6812e8f6a7ca2ea4d3d2191af3fd00b527fdc39321635ff751b42da321c79da3
Timestamp: 1764836145 Timestamp [UCT]: 2025-12-04 08:15:45 Age [y:d:h:m:s]: 00:054:17:39:01
Block: 1426137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39010 RingCT/type: yes/0
Extra: 016812e8f6a7ca2ea4d3d2191af3fd00b527fdc39321635ff751b42da321c79da302110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 606e9b10d463473ad8628bb451cfb2050d82271e095356db78c5ad1ad88dd39b 0.600000000000 1914820 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": 1426147, "vin": [ { "gen": { "height": 1426137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "606e9b10d463473ad8628bb451cfb2050d82271e095356db78c5ad1ad88dd39b" } } ], "extra": [ 1, 104, 18, 232, 246, 167, 202, 46, 164, 211, 210, 25, 26, 243, 253, 0, 181, 39, 253, 195, 147, 33, 99, 95, 247, 81, 180, 45, 163, 33, 199, 157, 163, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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