Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e138a0622445c058e30492ba4e4facc95f214e154d3bb2bdc8d97aa41c53ca2d

Tx prefix hash: 81a22183ddb99917911529b6bbe46bed447554f7064d0a0052281a6dcdd61cf0
Tx public key: 269d4c2ff7bfc45501125b73ddfd8b9f0f26b05f258078b307fae560f13e84e3
Timestamp: 1751000666 Timestamp [UCT]: 2025-06-27 05:04:26 Age [y:d:h:m:s]: 00:146:19:20:54
Block: 1313658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102924 RingCT/type: yes/0
Extra: 01269d4c2ff7bfc45501125b73ddfd8b9f0f26b05f258078b307fae560f13e84e3021100000010bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dab184752ffe9fc15b164ac1b2e8767a50c0e9c9e65bbf4d7790c78cbbbde896 0.600000000000 1801299 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": 1313668, "vin": [ { "gen": { "height": 1313658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dab184752ffe9fc15b164ac1b2e8767a50c0e9c9e65bbf4d7790c78cbbbde896" } } ], "extra": [ 1, 38, 157, 76, 47, 247, 191, 196, 85, 1, 18, 91, 115, 221, 253, 139, 159, 15, 38, 176, 95, 37, 128, 120, 179, 7, 250, 229, 96, 241, 62, 132, 227, 2, 17, 0, 0, 0, 16, 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