Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a9d8ae34e9724bfaea86f7a0f122ebe748447fd86962492e3913123318613e4

Tx prefix hash: 58eea4ba1787010f95e313712b5a7ec3c7311d785e8843f6049a62933a0bf13b
Tx public key: 63f9b08f5a2779a55e631ee6e6a218f658ad274b04c48545c1d87e10537fc7ab
Timestamp: 1750238597 Timestamp [UCT]: 2025-06-18 09:23:17 Age [y:d:h:m:s]: 00:154:22:55:46
Block: 1307565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108548 RingCT/type: yes/0
Extra: 0163f9b08f5a2779a55e631ee6e6a218f658ad274b04c48545c1d87e10537fc7ab021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39964f7778465dd2bee16ec43a624a57f88d82e44523f559160251cfc8f58aa8 0.600000000000 1795176 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": 1307575, "vin": [ { "gen": { "height": 1307565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39964f7778465dd2bee16ec43a624a57f88d82e44523f559160251cfc8f58aa8" } } ], "extra": [ 1, 99, 249, 176, 143, 90, 39, 121, 165, 94, 99, 30, 230, 230, 162, 24, 246, 88, 173, 39, 75, 4, 196, 133, 69, 193, 216, 126, 16, 83, 127, 199, 171, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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