Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18a71f5ed641f567456850bf040df224c8fbbeed74b0040b1618800d723fec1f

Tx prefix hash: 7c1eaefa8acd1cfd6294c37e59f1ffa25b75d833d9e02b02ca6bb6b4b44149d9
Tx public key: 6722686ae989bbaa764f39e181fcee8887dbeae9718ae3dbeb7a21710ee079b7
Timestamp: 1722199221 Timestamp [UCT]: 2024-07-28 20:40:21 Age [y:d:h:m:s]: 00:305:08:50:05
Block: 1075785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218194 RingCT/type: yes/0
Extra: 016722686ae989bbaa764f39e181fcee8887dbeae9718ae3dbeb7a21710ee079b702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 017d42856a5af380b842e630ce87fb8b9dd8863b62d943b137d3a8b93162474f 0.600000000000 1548314 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": 1075795, "vin": [ { "gen": { "height": 1075785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "017d42856a5af380b842e630ce87fb8b9dd8863b62d943b137d3a8b93162474f" } } ], "extra": [ 1, 103, 34, 104, 106, 233, 137, 187, 170, 118, 79, 57, 225, 129, 252, 238, 136, 135, 219, 234, 233, 113, 138, 227, 219, 235, 122, 33, 113, 14, 224, 121, 183, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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