Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa69f51935971c85a08b6c350c272307f11a958f0bf90dc3989d93dd552e11e7

Tx prefix hash: a3b90931a4b549c73ae8884f2ba9e5ffdcc7867926d76e4f65c554741c68d625
Tx public key: d5fb6abcede4a05c47dcc31e853959763b222b84cd327550b5ac8c1d553defa9
Timestamp: 1750195553 Timestamp [UCT]: 2025-06-17 21:25:53 Age [y:d:h:m:s]: 00:156:12:09:57
Block: 1307206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109650 RingCT/type: yes/0
Extra: 01d5fb6abcede4a05c47dcc31e853959763b222b84cd327550b5ac8c1d553defa902110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2011627323bda306bb6b1d369591d37eb2b8f234ec3e1fc1dfbaf6d57c91a5f 0.600000000000 1794815 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": 1307216, "vin": [ { "gen": { "height": 1307206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2011627323bda306bb6b1d369591d37eb2b8f234ec3e1fc1dfbaf6d57c91a5f" } } ], "extra": [ 1, 213, 251, 106, 188, 237, 228, 160, 92, 71, 220, 195, 30, 133, 57, 89, 118, 59, 34, 43, 132, 205, 50, 117, 80, 181, 172, 140, 29, 85, 61, 239, 169, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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