Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35616e10e54701f53bb6132cf1162fd8da8ac56c07365b0d51f7f6d4184cec47

Tx prefix hash: 3e5366f5c8faeb37d657e857aba5f32712450b9f752dffaeef2d7d2138287f15
Tx public key: f41e342eb8a805a0ab4f637a35be1a8f921d7b9aa19b3c6d94f8b139d86d57a7
Timestamp: 1731885401 Timestamp [UCT]: 2024-11-17 23:16:41 Age [y:d:h:m:s]: 00:119:03:32:00
Block: 1156002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84972 RingCT/type: yes/0
Extra: 01f41e342eb8a805a0ab4f637a35be1a8f921d7b9aa19b3c6d94f8b139d86d57a7021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6907fd80f3cf56945c70a15ff662487071cf8c777fe4b54fda9c0e5e96e7e3fe 0.600000000000 1641621 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": 1156012, "vin": [ { "gen": { "height": 1156002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6907fd80f3cf56945c70a15ff662487071cf8c777fe4b54fda9c0e5e96e7e3fe" } } ], "extra": [ 1, 244, 30, 52, 46, 184, 168, 5, 160, 171, 79, 99, 122, 53, 190, 26, 143, 146, 29, 123, 154, 161, 155, 60, 109, 148, 248, 177, 57, 216, 109, 87, 167, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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