Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e48700d693a58777c71986a9e491c7b9d7ae5c9f082951d93b0c1d1a414dc74a

Tx prefix hash: 7fa5bd2d96566116a4c005d936c3c9ba9c5ae3eb7e74299e77128ff5655a0e46
Tx public key: f9626a13f168b35bd268f26994e0c40e2142d9aa01af2196870422b36be5b8e1
Timestamp: 1583634616 Timestamp [UCT]: 2020-03-08 02:30:16 Age [y:d:h:m:s]: 04:296:11:10:13
Block: 78383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106652 RingCT/type: yes/0
Extra: 01f9626a13f168b35bd268f26994e0c40e2142d9aa01af2196870422b36be5b8e102110000000381a90efe000000000000000000

1 output(s) for total of 337.509013045000 dcy

stealth address amount amount idx
00: 316e3389e56b83e5b026eed3629b5862fd1e3c697dc9de763512bde249dfaf3a 337.509013045000 143827 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": 78393, "vin": [ { "gen": { "height": 78383 } } ], "vout": [ { "amount": 337509013045, "target": { "key": "316e3389e56b83e5b026eed3629b5862fd1e3c697dc9de763512bde249dfaf3a" } } ], "extra": [ 1, 249, 98, 106, 19, 241, 104, 179, 91, 210, 104, 242, 105, 148, 224, 196, 14, 33, 66, 217, 170, 1, 175, 33, 150, 135, 4, 34, 179, 107, 229, 184, 225, 2, 17, 0, 0, 0, 3, 129, 169, 14, 254, 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