Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28ca42b1884c76de684fb1ce0e44c9e0172e4aa9aab9676b06b2b58a5c2a3a64

Tx prefix hash: 6faf0aca1330aa7a4add3dcd342f3ea467d92f860b276ca312837fcad6e40d86
Tx public key: 9b575ef82c8d74ffa1e97f8439ce6b09ec75de61b29314548bf689ecc58da677
Timestamp: 1695774153 Timestamp [UCT]: 2023-09-27 00:22:33 Age [y:d:h:m:s]: 01:241:09:52:22
Block: 856908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433640 RingCT/type: yes/0
Extra: 019b575ef82c8d74ffa1e97f8439ce6b09ec75de61b29314548bf689ecc58da67702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.888603712000 dcy

stealth address amount amount idx
00: 8856f2a6a02726a4d5bd7925babb52a1768d93e72f8da900822748100098c0d6 0.888603712000 1311002 of 0

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": 856918, "vin": [ { "gen": { "height": 856908 } } ], "vout": [ { "amount": 888603712, "target": { "key": "8856f2a6a02726a4d5bd7925babb52a1768d93e72f8da900822748100098c0d6" } } ], "extra": [ 1, 155, 87, 94, 248, 44, 141, 116, 255, 161, 233, 127, 132, 57, 206, 107, 9, 236, 117, 222, 97, 178, 147, 20, 84, 139, 246, 137, 236, 197, 141, 166, 119, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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