Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72021f273d5a6e6fef6ad79f9d0169fcf7b4d55c25e6764fa0aaa18c04edc4e

Tx prefix hash: 5a4499778bbca35e77053140477670c2e5330a72c43cd2f8f4ba9714bc99f90c
Tx public key: 4a44bd1db0b918922a843e0fab9085683ba5bed068c5e16585ae79b4861333ef
Timestamp: 1577557773 Timestamp [UCT]: 2019-12-28 18:29:33 Age [y:d:h:m:s]: 05:122:05:01:27
Block: 33704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1237211 RingCT/type: yes/0
Extra: 014a44bd1db0b918922a843e0fab9085683ba5bed068c5e16585ae79b4861333ef0211000000129159db1e000000000000000000

1 output(s) for total of 474.605743735000 dcy

stealth address amount amount idx
00: 5e94f9b7389823d501ba889016517d48adf75d64faeb9430353819f95760d3d7 474.605743735000 56527 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": 33714, "vin": [ { "gen": { "height": 33704 } } ], "vout": [ { "amount": 474605743735, "target": { "key": "5e94f9b7389823d501ba889016517d48adf75d64faeb9430353819f95760d3d7" } } ], "extra": [ 1, 74, 68, 189, 29, 176, 185, 24, 146, 42, 132, 62, 15, 171, 144, 133, 104, 59, 165, 190, 208, 104, 197, 225, 101, 133, 174, 121, 180, 134, 19, 51, 239, 2, 17, 0, 0, 0, 18, 145, 89, 219, 30, 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