Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26734c8e6f3d4ece708f512833b7ca084a456b4a19e7cab2c568e7d1d505f0ae

Tx prefix hash: eb99e09437d3463c1f3b5380b402d09e0c39fa6b2142d23d3eb487301ae1c18b
Tx public key: a4b4ab43c766468bf685717815b84f9c8014b630e54f40a72a44ab29163c18f7
Timestamp: 1758488915 Timestamp [UCT]: 2025-09-21 21:08:35 Age [y:d:h:m:s]: 00:097:19:54:16
Block: 1373534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70051 RingCT/type: yes/0
Extra: 01a4b4ab43c766468bf685717815b84f9c8014b630e54f40a72a44ab29163c18f7021100000008ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36ca280e6020a8c2ea0e4ef728f84325650a116ff3d0644a444a985c5fcd6082 0.600000000000 1861619 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": 1373544, "vin": [ { "gen": { "height": 1373534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36ca280e6020a8c2ea0e4ef728f84325650a116ff3d0644a444a985c5fcd6082" } } ], "extra": [ 1, 164, 180, 171, 67, 199, 102, 70, 139, 246, 133, 113, 120, 21, 184, 79, 156, 128, 20, 182, 48, 229, 79, 64, 167, 42, 68, 171, 41, 22, 60, 24, 247, 2, 17, 0, 0, 0, 8, 173, 121, 72, 208, 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