Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 393bd42a758c69a069bfce665d876f615a5a9480027d316eca61771cd59feef3

Tx prefix hash: 1e44c1dc8e81973677e31d59fd87218488349fb2c3340ec153306a627341f3f6
Tx public key: 982cad3ec9d168d3d131daab25389a4e7f443f8392897f081fdd2b641d1711cd
Timestamp: 1694981559 Timestamp [UCT]: 2023-09-17 20:12:39 Age [y:d:h:m:s]: 01:127:22:55:57
Block: 850331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352718 RingCT/type: yes/0
Extra: 01982cad3ec9d168d3d131daab25389a4e7f443f8392897f081fdd2b641d1711cd021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.934330366000 dcy

stealth address amount amount idx
00: 77e3e5b42f3da97c360f54d972f4567e57866a934a96bef60f0c41b6a8de45af 0.934330366000 1304045 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": 850341, "vin": [ { "gen": { "height": 850331 } } ], "vout": [ { "amount": 934330366, "target": { "key": "77e3e5b42f3da97c360f54d972f4567e57866a934a96bef60f0c41b6a8de45af" } } ], "extra": [ 1, 152, 44, 173, 62, 201, 209, 104, 211, 209, 49, 218, 171, 37, 56, 154, 78, 127, 68, 63, 131, 146, 137, 127, 8, 31, 221, 43, 100, 29, 23, 17, 205, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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