Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa95beb047b9bd36be776e6296d56354afe87b3a6f35c2fec69d17faef53c79

Tx prefix hash: 324d6eefe773615ef27111459ebade778b7afd7638b76ea42f15131bb0ea6635
Tx public key: 262090c4e088cc0f14d2db396a60efda0df525f8e26291f621ab871fda7b3129
Timestamp: 1724260158 Timestamp [UCT]: 2024-08-21 17:09:18 Age [y:d:h:m:s]: 00:206:19:07:20
Block: 1092888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147662 RingCT/type: yes/0
Extra: 01262090c4e088cc0f14d2db396a60efda0df525f8e26291f621ab871fda7b3129021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87c79c39821aab2fa3b39a5941df2ed7986428896d6a9c81cb7561c6f056e853 0.600000000000 1567723 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": 1092898, "vin": [ { "gen": { "height": 1092888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87c79c39821aab2fa3b39a5941df2ed7986428896d6a9c81cb7561c6f056e853" } } ], "extra": [ 1, 38, 32, 144, 196, 224, 136, 204, 15, 20, 210, 219, 57, 106, 96, 239, 218, 13, 245, 37, 248, 226, 98, 145, 246, 33, 171, 135, 31, 218, 123, 49, 41, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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