Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b25e742cd2ae3c3f9179bce42e93be0792d04bccee34c6614897882e811ec0c

Tx prefix hash: 98ca717ad6af1e3180a7b089ce1de7b772cd24a766053831d157f6b2e274ccdb
Tx public key: 2aa5fc0e2f5625e7282893211fda7fb8f145ae0c011518a526915acfb7eda958
Timestamp: 1765042840 Timestamp [UCT]: 2025-12-06 17:40:40 Age [y:d:h:m:s]: 00:032:23:47:02
Block: 1427847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23631 RingCT/type: yes/0
Extra: 012aa5fc0e2f5625e7282893211fda7fb8f145ae0c011518a526915acfb7eda958021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b48324a2465965b0226b314f6397103044638252a14760ecfb9468e852ca8a1f 0.600000000000 1916554 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": 1427857, "vin": [ { "gen": { "height": 1427847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b48324a2465965b0226b314f6397103044638252a14760ecfb9468e852ca8a1f" } } ], "extra": [ 1, 42, 165, 252, 14, 47, 86, 37, 231, 40, 40, 147, 33, 31, 218, 127, 184, 241, 69, 174, 12, 1, 21, 24, 165, 38, 145, 90, 207, 183, 237, 169, 88, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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