Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44b34f3c59e9f42317e631b8aa511268b604828d8354a054e4f58a57abf2342a

Tx prefix hash: bfd024117fe540d35055ae5967f9bdc6a317c01372cbc3ca917cc4342ca3b282
Tx public key: 968bcb27ef9b1869533d01e3424f31e963efd4230c23fda72d5d2bf4616fa80a
Timestamp: 1759186477 Timestamp [UCT]: 2025-09-29 22:54:37 Age [y:d:h:m:s]: 00:050:20:14:22
Block: 1379311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36411 RingCT/type: yes/0
Extra: 01968bcb27ef9b1869533d01e3424f31e963efd4230c23fda72d5d2bf4616fa80a021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 206702bd077cf12910f911267ec4e308ed18c139e4f73c1358fb0b5f090b36c9 0.600000000000 1867408 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": 1379321, "vin": [ { "gen": { "height": 1379311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "206702bd077cf12910f911267ec4e308ed18c139e4f73c1358fb0b5f090b36c9" } } ], "extra": [ 1, 150, 139, 203, 39, 239, 155, 24, 105, 83, 61, 1, 227, 66, 79, 49, 233, 99, 239, 212, 35, 12, 35, 253, 167, 45, 93, 43, 244, 97, 111, 168, 10, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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