Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de142260cc09f8930a1638641c27cbad9602f6c75d409377277adbad5b64eee9

Tx prefix hash: 588633bfc67a8b79a90e72ad2250674e2074e3e30c10231070006240605c10fe
Tx public key: a9610f95d3b0dbf4f15bd217cd5f5a49b60d223dcdd9d8ec5e151a5f91c4c693
Timestamp: 1677059112 Timestamp [UCT]: 2023-02-22 09:45:12 Age [y:d:h:m:s]: 02:097:19:30:07
Block: 702432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591541 RingCT/type: yes/0
Extra: 01a9610f95d3b0dbf4f15bd217cd5f5a49b60d223dcdd9d8ec5e151a5f91c4c69302110000000174b6d784000000000000000000

1 output(s) for total of 2.887693533000 dcy

stealth address amount amount idx
00: 8403bb0eb49aee6192f136654dbd3dc2418d64e3b434bd6148e3bdfa80069e7a 2.887693533000 1145935 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": 702442, "vin": [ { "gen": { "height": 702432 } } ], "vout": [ { "amount": 2887693533, "target": { "key": "8403bb0eb49aee6192f136654dbd3dc2418d64e3b434bd6148e3bdfa80069e7a" } } ], "extra": [ 1, 169, 97, 15, 149, 211, 176, 219, 244, 241, 91, 210, 23, 205, 95, 90, 73, 182, 13, 34, 61, 205, 217, 216, 236, 94, 21, 26, 95, 145, 196, 198, 147, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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