Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0114b9f9d92ae2adcd143bfaa529195b2a832cbbe7162e8cbe351fafe853713b

Tx prefix hash: 632a770f6c0d41960fd7fa04ed51450b9daf8a18500b7b7fa00d3f005fd373f6
Tx public key: 8e08723ded9d692c44966e11ad267477a52645cb18fa8b24ebb2effea371e193
Timestamp: 1730009286 Timestamp [UCT]: 2024-10-27 06:08:06 Age [y:d:h:m:s]: 00:165:16:37:38
Block: 1140506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118212 RingCT/type: yes/0
Extra: 018e08723ded9d692c44966e11ad267477a52645cb18fa8b24ebb2effea371e193021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f3f778d7cc5e2cb5b3af3d6a20aa0e4d98c26db2c130dbcfe9279ca08e6a774 0.600000000000 1624305 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": 1140516, "vin": [ { "gen": { "height": 1140506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f3f778d7cc5e2cb5b3af3d6a20aa0e4d98c26db2c130dbcfe9279ca08e6a774" } } ], "extra": [ 1, 142, 8, 114, 61, 237, 157, 105, 44, 68, 150, 110, 17, 173, 38, 116, 119, 165, 38, 69, 203, 24, 250, 139, 36, 235, 178, 239, 254, 163, 113, 225, 147, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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