Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855f7afa69dec745aa6d332b7eb4f814818902c597cf74243c3b6a783ecf4344

Tx prefix hash: af4e070f0fa2adf5236aa6bb6fb6afb2414a0b57c9832d586a929b091b756261
Tx public key: 64490aa6369ebfc56fb09f7e88815e724bbd0fb9d2586d465cdfff505f5c1a85
Timestamp: 1717463285 Timestamp [UCT]: 2024-06-04 01:08:05 Age [y:d:h:m:s]: 00:361:15:39:00
Block: 1036529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258509 RingCT/type: yes/0
Extra: 0164490aa6369ebfc56fb09f7e88815e724bbd0fb9d2586d465cdfff505f5c1a850211000000044385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c8637ca777d376b7f00093abd668364c341ac53b115e9c352bce2b7c7891257 0.600000000000 1505056 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": 1036539, "vin": [ { "gen": { "height": 1036529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c8637ca777d376b7f00093abd668364c341ac53b115e9c352bce2b7c7891257" } } ], "extra": [ 1, 100, 73, 10, 166, 54, 158, 191, 197, 111, 176, 159, 126, 136, 129, 94, 114, 75, 189, 15, 185, 210, 88, 109, 70, 92, 223, 255, 80, 95, 92, 26, 133, 2, 17, 0, 0, 0, 4, 67, 133, 54, 42, 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