Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222bef2d4e088b8996690a4dfa5ebff0dc65a4577203f6051d255ebab070f0d1

Tx prefix hash: b1de42538f22ee8ddd529123f3180bc4544d677a1d969f34c39f48c084683319
Tx public key: 6d62df77f10e621f154e088d030f182c9b782a454672ed7437f972a2417da46a
Timestamp: 1751147781 Timestamp [UCT]: 2025-06-28 21:56:21 Age [y:d:h:m:s]: 00:140:04:31:49
Block: 1314787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98292 RingCT/type: yes/0
Extra: 016d62df77f10e621f154e088d030f182c9b782a454672ed7437f972a2417da46a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bb57556d8572ee0f6c8c62c0ec50fd18a5bccea77ff723cb61beaec15a23ae0 0.600000000000 1802438 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": 1314797, "vin": [ { "gen": { "height": 1314787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bb57556d8572ee0f6c8c62c0ec50fd18a5bccea77ff723cb61beaec15a23ae0" } } ], "extra": [ 1, 109, 98, 223, 119, 241, 14, 98, 31, 21, 78, 8, 141, 3, 15, 24, 44, 155, 120, 42, 69, 70, 114, 237, 116, 55, 249, 114, 162, 65, 125, 164, 106, 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