Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57e7036e7b85b51f2feec79c216e73ba24d57f1f772e0e1b086682c0ded72662

Tx prefix hash: 5c7002401b0e1a4ddfecc830930453b7c4eb5786f8340d01aa832e8bf23f6ff0
Tx public key: 519f5e48e528546cfd65e46488c9f047953b9060713879893b07f8ea27dcb658
Timestamp: 1582044427 Timestamp [UCT]: 2020-02-18 16:47:07 Age [y:d:h:m:s]: 05:023:22:06:23
Block: 67674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170087 RingCT/type: yes/0
Extra: 01519f5e48e528546cfd65e46488c9f047953b9060713879893b07f8ea27dcb658021100000004d81c26c0000000000000000000

1 output(s) for total of 366.242510461000 dcy

stealth address amount amount idx
00: 02baa8440fadbc82df97331147d773dca3ff23521ef5ccbc5ae01bc340e03b1a 366.242510461000 124623 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": 67684, "vin": [ { "gen": { "height": 67674 } } ], "vout": [ { "amount": 366242510461, "target": { "key": "02baa8440fadbc82df97331147d773dca3ff23521ef5ccbc5ae01bc340e03b1a" } } ], "extra": [ 1, 81, 159, 94, 72, 229, 40, 84, 108, 253, 101, 228, 100, 136, 201, 240, 71, 149, 59, 144, 96, 113, 56, 121, 137, 59, 7, 248, 234, 39, 220, 182, 88, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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