Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 358801907e14a630ac951012d962972e6dbb36e00d18af3972896ed6a341f4e7

Tx prefix hash: dc437eaf7099b4b6ca9f7f3b13efaee704baecbfc4f5dc95c0cd922cf148e755
Tx public key: 703112b8dfd9328a05d0dceaf14daad6836610bd7b1a475b5aa834cb4740339b
Timestamp: 1580977411 Timestamp [UCT]: 2020-02-06 08:23:31 Age [y:d:h:m:s]: 05:027:23:30:39
Block: 59721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172094 RingCT/type: yes/0
Extra: 01703112b8dfd9328a05d0dceaf14daad6836610bd7b1a475b5aa834cb4740339b0211000000047adf42d3000000000000000000

1 output(s) for total of 389.172144532000 dcy

stealth address amount amount idx
00: 352054a8435376638c878780321a770a85a30af052fcf997792481ef3a2582a6 389.172144532000 110204 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": 59731, "vin": [ { "gen": { "height": 59721 } } ], "vout": [ { "amount": 389172144532, "target": { "key": "352054a8435376638c878780321a770a85a30af052fcf997792481ef3a2582a6" } } ], "extra": [ 1, 112, 49, 18, 184, 223, 217, 50, 138, 5, 208, 220, 234, 241, 77, 170, 214, 131, 102, 16, 189, 123, 26, 71, 91, 90, 168, 52, 203, 71, 64, 51, 155, 2, 17, 0, 0, 0, 4, 122, 223, 66, 211, 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