Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392af8699f3feac8bf5c248529f3da8b81899c81b4b51435fb83723819136465

Tx prefix hash: 457c2870759720d757f95df7f3d23a3329db83268dffa9a57ce4e90ee6bb0b9c
Tx public key: 8e6cba02d3d202b39b3bf3f0431ffcf1c3a15e2c9f0a38bb6ad9688dde416f9f
Timestamp: 1576644094 Timestamp [UCT]: 2019-12-18 04:41:34 Age [y:d:h:m:s]: 05:123:09:58:40
Block: 28517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1235691 RingCT/type: yes/0
Extra: 018e6cba02d3d202b39b3bf3f0431ffcf1c3a15e2c9f0a38bb6ad9688dde416f9f02110000001d9159db1e000000000000000000

1 output(s) for total of 493.755794654000 dcy

stealth address amount amount idx
00: d1d5d5ffc0fe7c65d7c076d706fb41b38e409f514c0ebe2c66607d1b1081801d 493.755794654000 47067 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": 28527, "vin": [ { "gen": { "height": 28517 } } ], "vout": [ { "amount": 493755794654, "target": { "key": "d1d5d5ffc0fe7c65d7c076d706fb41b38e409f514c0ebe2c66607d1b1081801d" } } ], "extra": [ 1, 142, 108, 186, 2, 211, 210, 2, 179, 155, 59, 243, 240, 67, 31, 252, 241, 195, 161, 94, 44, 159, 10, 56, 187, 106, 217, 104, 141, 222, 65, 111, 159, 2, 17, 0, 0, 0, 29, 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