Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a2e3cc6b9e3bab4cb7fc09dfc57eb4507a8f6deea8f6e55d23240005da1b851

Tx prefix hash: ff7de9e1bb24db97f69a91c13129a559d0711ad5e9d53a1107b44e10e538a192
Tx public key: 074b8e245284d35a4a42e5aba4e908799915f271dad13d3e2017e45176049246
Timestamp: 1676304731 Timestamp [UCT]: 2023-02-13 16:12:11 Age [y:d:h:m:s]: 02:012:09:24:39
Block: 696188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530414 RingCT/type: yes/0
Extra: 01074b8e245284d35a4a42e5aba4e908799915f271dad13d3e2017e4517604924602110000000333af99f4000000000000000000

1 output(s) for total of 3.028587137000 dcy

stealth address amount amount idx
00: f5176cfbb3f3215a1dea20c75b9a64b5d3dafeb87ef48018ed2fad7923e88302 3.028587137000 1139157 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": 696198, "vin": [ { "gen": { "height": 696188 } } ], "vout": [ { "amount": 3028587137, "target": { "key": "f5176cfbb3f3215a1dea20c75b9a64b5d3dafeb87ef48018ed2fad7923e88302" } } ], "extra": [ 1, 7, 75, 142, 36, 82, 132, 211, 90, 74, 66, 229, 171, 164, 233, 8, 121, 153, 21, 242, 113, 218, 209, 61, 62, 32, 23, 228, 81, 118, 4, 146, 70, 2, 17, 0, 0, 0, 3, 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