Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10121e58a596a278796548e05e9c2fc382ae4c1034119676d2d1fbcef2ab0929

Tx prefix hash: ae16dcd3d0ae39e85e7c971a945597c3ad1f7b8ddae3ea60e4a08713b4b213af
Tx public key: abf32feece4bfc997caec79e4e41a7689d37ebd615706fab58440483258fd3b0
Timestamp: 1745782363 Timestamp [UCT]: 2025-04-27 19:32:43 Age [y:d:h:m:s]: 00:202:21:04:27
Block: 1270791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142704 RingCT/type: yes/0
Extra: 01abf32feece4bfc997caec79e4e41a7689d37ebd615706fab58440483258fd3b00211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: febbbc8b2976c25d10b346b96b30a806662a667132e237bcbf761d9bdc0ed7b8 0.600000000000 1758036 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": 1270801, "vin": [ { "gen": { "height": 1270791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "febbbc8b2976c25d10b346b96b30a806662a667132e237bcbf761d9bdc0ed7b8" } } ], "extra": [ 1, 171, 243, 47, 238, 206, 75, 252, 153, 124, 174, 199, 158, 78, 65, 167, 104, 157, 55, 235, 214, 21, 112, 111, 171, 88, 68, 4, 131, 37, 143, 211, 176, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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