Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6280b5f07235724180371f7b02f10045b291e7d0f1de13bc20c67d674d1f3139

Tx prefix hash: 06d03011200fb9f58bb2905f348a21a1d30609a8d17b8f2bbd47a227e0fe7f8f
Tx public key: 6fefead5d8c2ebf8da65d20e32db528222b1835cce4642b8384843a633483d15
Timestamp: 1584903338 Timestamp [UCT]: 2020-03-22 18:55:38 Age [y:d:h:m:s]: 04:228:18:46:57
Block: 86568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1060552 RingCT/type: yes/0
Extra: 016fefead5d8c2ebf8da65d20e32db528222b1835cce4642b8384843a633483d150211000000978c5f723a000000000000000000

1 output(s) for total of 317.088193442000 dcy

stealth address amount amount idx
00: 507afd92b11a259fc2adbe9d4a24ab902af175238ae137c978ff35cb825c05b0 317.088193442000 156194 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": 86578, "vin": [ { "gen": { "height": 86568 } } ], "vout": [ { "amount": 317088193442, "target": { "key": "507afd92b11a259fc2adbe9d4a24ab902af175238ae137c978ff35cb825c05b0" } } ], "extra": [ 1, 111, 239, 234, 213, 216, 194, 235, 248, 218, 101, 210, 14, 50, 219, 82, 130, 34, 177, 131, 92, 206, 70, 66, 184, 56, 72, 67, 166, 51, 72, 61, 21, 2, 17, 0, 0, 0, 151, 140, 95, 114, 58, 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