Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88e6ae254b754ce7962a4a3a4fd62cb2150e712b9b77fe829363d2fb485d1769

Tx prefix hash: d72360b43a27360aa90dbb020eb5ac273154a1645384459ad358850ea259d29a
Tx public key: 765dfbcb101d62abb557d43b728549bd5e1623b86cb492e3e5a84079d25e8009
Timestamp: 1713695297 Timestamp [UCT]: 2024-04-21 10:28:17 Age [y:d:h:m:s]: 00:330:00:42:21
Block: 1005286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235946 RingCT/type: yes/0
Extra: 01765dfbcb101d62abb557d43b728549bd5e1623b86cb492e3e5a84079d25e800902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1d52b9e53883d36d733d49ce3b3a3c1a645010fc23425e8e922c8ce66c9afe5 0.600000000000 1465872 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": 1005296, "vin": [ { "gen": { "height": 1005286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1d52b9e53883d36d733d49ce3b3a3c1a645010fc23425e8e922c8ce66c9afe5" } } ], "extra": [ 1, 118, 93, 251, 203, 16, 29, 98, 171, 181, 87, 212, 59, 114, 133, 73, 189, 94, 22, 35, 184, 108, 180, 146, 227, 229, 168, 64, 121, 210, 94, 128, 9, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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