Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcf62258f70308c78b773fce48384b80b8662dbcc38ea5c539674bd9db69209c

Tx prefix hash: 488edb9ad2600d91b2b5f89817e0966381a383336201747f143c541d643c2185
Tx public key: ebbbb5d1236b6a8655cb3e3e3f4ca0a629ad892117fb3f5a4088fbe7494f1c0f
Timestamp: 1672136214 Timestamp [UCT]: 2022-12-27 10:16:54 Age [y:d:h:m:s]: 01:342:23:21:42
Block: 661595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506160 RingCT/type: yes/0
Extra: 01ebbbb5d1236b6a8655cb3e3e3f4ca0a629ad892117fb3f5a4088fbe7494f1c0f0211000000017e406890000000000000000000

1 output(s) for total of 3.943311573000 dcy

stealth address amount amount idx
00: 40293a90ab39a44c4f5e1f963da927b77f5b638283b7203aa80554e80a7275a2 3.943311573000 1102378 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": 661605, "vin": [ { "gen": { "height": 661595 } } ], "vout": [ { "amount": 3943311573, "target": { "key": "40293a90ab39a44c4f5e1f963da927b77f5b638283b7203aa80554e80a7275a2" } } ], "extra": [ 1, 235, 187, 181, 209, 35, 107, 106, 134, 85, 203, 62, 62, 63, 76, 160, 166, 41, 173, 137, 33, 23, 251, 63, 90, 64, 136, 251, 231, 73, 79, 28, 15, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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