Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047a3caa339eddada0e513811b2ca81f4b32d26a1d70c1f90633f9a3f1d75d29

Tx prefix hash: f389a5473244b14df2c01db6af5ea8f2e2e5d565e024636400a093d264b0bff9
Tx public key: e30bf02f0d3cce24fd9a90a1641cb508d33c251c30211dd6dc8adb3fa886692b
Timestamp: 1730832611 Timestamp [UCT]: 2024-11-05 18:50:11 Age [y:d:h:m:s]: 01:004:05:54:40
Block: 1147270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261461 RingCT/type: yes/0
Extra: 01e30bf02f0d3cce24fd9a90a1641cb508d33c251c30211dd6dc8adb3fa886692b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc75b472949d2bb30f3003c7e1424e7e917a77f2190710dfc796c047787fe822 0.600000000000 1631965 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": 1147280, "vin": [ { "gen": { "height": 1147270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc75b472949d2bb30f3003c7e1424e7e917a77f2190710dfc796c047787fe822" } } ], "extra": [ 1, 227, 11, 240, 47, 13, 60, 206, 36, 253, 154, 144, 161, 100, 28, 181, 8, 211, 60, 37, 28, 48, 33, 29, 214, 220, 138, 219, 63, 168, 134, 105, 43, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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