Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27b17f09f6e1b4aea3777b6dfcc903f7a2401f30c68dbf801776176238baff87

Tx prefix hash: 0162741edcd9aefd58b58424189195f2bf27b44095bbd174cd9a6bd986225a0a
Tx public key: 459742f6a0a5e58c9939e13aa1479d2fd7a04844a4a14a6725dc60832d00dbde
Timestamp: 1749700519 Timestamp [UCT]: 2025-06-12 03:55:19 Age [y:d:h:m:s]: 00:155:04:57:07
Block: 1303201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108639 RingCT/type: yes/0
Extra: 01459742f6a0a5e58c9939e13aa1479d2fd7a04844a4a14a6725dc60832d00dbde021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49fb07df8751d4480cb1ca24c9e15acd69765d2187b818c4cdf43faee22f53c7 0.600000000000 1790778 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": 1303211, "vin": [ { "gen": { "height": 1303201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49fb07df8751d4480cb1ca24c9e15acd69765d2187b818c4cdf43faee22f53c7" } } ], "extra": [ 1, 69, 151, 66, 246, 160, 165, 229, 140, 153, 57, 225, 58, 161, 71, 157, 47, 215, 160, 72, 68, 164, 161, 74, 103, 37, 220, 96, 131, 45, 0, 219, 222, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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