Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e757cf65ed7472b955643cec729d621d05577b1dbe5a929404f137910cd02db1

Tx prefix hash: 8cb484a1863621dcbb8af89f04543947ebdee6571fae7ac859a63fcf53ff0fb6
Tx public key: d87442b356749196c468140a92cc1478a4c0df1bf1fddc5bd48fbe8ac9951c1c
Timestamp: 1582101025 Timestamp [UCT]: 2020-02-19 08:30:25 Age [y:d:h:m:s]: 04:355:22:26:02
Block: 68012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146607 RingCT/type: yes/0
Extra: 01d87442b356749196c468140a92cc1478a4c0df1bf1fddc5bd48fbe8ac9951c1c02110000000212c4732d000000000000000000

1 output(s) for total of 365.307611046000 dcy

stealth address amount amount idx
00: 1b08f3984202d4913ad88a7430aa12205407b57eeabd24bcc5dcec6b28aa0f91 365.307611046000 125280 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": 68022, "vin": [ { "gen": { "height": 68012 } } ], "vout": [ { "amount": 365307611046, "target": { "key": "1b08f3984202d4913ad88a7430aa12205407b57eeabd24bcc5dcec6b28aa0f91" } } ], "extra": [ 1, 216, 116, 66, 179, 86, 116, 145, 150, 196, 104, 20, 10, 146, 204, 20, 120, 164, 192, 223, 27, 241, 253, 220, 91, 212, 143, 190, 138, 201, 149, 28, 28, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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