Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e962658783bc21c2b2d8535453f40e1e309356391918950ea7d5bf5b5e9e0f0

Tx prefix hash: 1575ed790b63b437493105de9c8a6cec87ea4978a8da364b9f793cced4d4ba20
Tx public key: 114b61d8d271fd20b658ca65ed03bdce863b97d550c1ab7527186a35094eebc2
Timestamp: 1578716844 Timestamp [UCT]: 2020-01-11 04:27:24 Age [y:d:h:m:s]: 05:299:02:21:00
Block: 43065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1361553 RingCT/type: yes/0
Extra: 01114b61d8d271fd20b658ca65ed03bdce863b97d550c1ab7527186a35094eebc20211000000164ac5aa02000000000000000000

1 output(s) for total of 441.884350376000 dcy

stealth address amount amount idx
00: 2e1ae4bd5127bc0d572c2f24058e23cbbf79506d3b1485b8c693b0d438dc6e60 441.884350376000 77821 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": 43075, "vin": [ { "gen": { "height": 43065 } } ], "vout": [ { "amount": 441884350376, "target": { "key": "2e1ae4bd5127bc0d572c2f24058e23cbbf79506d3b1485b8c693b0d438dc6e60" } } ], "extra": [ 1, 17, 75, 97, 216, 210, 113, 253, 32, 182, 88, 202, 101, 237, 3, 189, 206, 134, 59, 151, 213, 80, 193, 171, 117, 39, 24, 106, 53, 9, 78, 235, 194, 2, 17, 0, 0, 0, 22, 74, 197, 170, 2, 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