Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439e1ab0ce043e5167fad1bb389a9da0c1b87cf2c598816fe25d0349387fc76c

Tx prefix hash: ac5f1c8b3767b25dd0dafb2cc4c4858b0be579a036e0c8a6dfb9b2a1593e4ad4
Tx public key: a0eb0f7549c18207d51fa628dc00a9ccbe81f42299b26812a3d7f99b4f3e3b7c
Timestamp: 1702155356 Timestamp [UCT]: 2023-12-09 20:55:56 Age [y:d:h:m:s]: 01:142:23:06:32
Block: 909617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363323 RingCT/type: yes/0
Extra: 01a0eb0f7549c18207d51fa628dc00a9ccbe81f42299b26812a3d7f99b4f3e3b7c02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccbc3b97fcbd1d3b8bff5cda29fc98bd2401b801ed3ab49f6c1e62f19800964e 0.600000000000 1366718 of 15

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": 909627, "vin": [ { "gen": { "height": 909617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccbc3b97fcbd1d3b8bff5cda29fc98bd2401b801ed3ab49f6c1e62f19800964e" } } ], "extra": [ 1, 160, 235, 15, 117, 73, 193, 130, 7, 213, 31, 166, 40, 220, 0, 169, 204, 190, 129, 244, 34, 153, 178, 104, 18, 163, 215, 249, 155, 79, 62, 59, 124, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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