Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce49e3615c434cdf38190aa285c1fbc0802c9acfb15d162cacda464688ac43c5

Tx prefix hash: e0a000860f85ede57ed783ca1e106da01109c19ab71b4025b1cdaee08316dea7
Tx public key: c9723e53e92a6b843cd17b6756fd65acec855d818b36942968cd940cfc4c2efa
Timestamp: 1574136814 Timestamp [UCT]: 2019-11-19 04:13:34 Age [y:d:h:m:s]: 05:106:20:28:27
Block: 12412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1219184 RingCT/type: yes/0
Extra: 01c9723e53e92a6b843cd17b6756fd65acec855d818b36942968cd940cfc4c2efa02110000000466a80d00000000000000000000

1 output(s) for total of 558.321273734000 dcy

stealth address amount amount idx
00: a9ee5c3851e891ea9e50b82253e8abd690aeda93ad371211689ebdf4df3f6080 558.321273734000 13669 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": 12422, "vin": [ { "gen": { "height": 12412 } } ], "vout": [ { "amount": 558321273734, "target": { "key": "a9ee5c3851e891ea9e50b82253e8abd690aeda93ad371211689ebdf4df3f6080" } } ], "extra": [ 1, 201, 114, 62, 83, 233, 42, 107, 132, 60, 209, 123, 103, 86, 253, 101, 172, 236, 133, 93, 129, 139, 54, 148, 41, 104, 205, 148, 12, 252, 76, 46, 250, 2, 17, 0, 0, 0, 4, 102, 168, 13, 0, 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